home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: Borland C++ 5.0 and non-16-bit Debugger
- Date: 11 Apr 1996 19:10:34 GMT
- Organization: Borland International
- Message-ID: <4kjlfa$occ@druid.borland.com>
- References: <316D35AA.39A3@pixar.com>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <316D35AA.39A3@pixar.com>, nybble@pixar.com says...
- >
- >Can anyone explain _why_ Borland would decide to stop supporting 16-bit
- >applications in the new integrated debugger?!? The _only_ reason we use
- >Borland instead of Microsoft is because there is still a 16-bit market
- >out there. Version 4.5 was just perfect for this. However, while 5.0
- >will create 16-bit apps, you are forced to use the Turbo Debugger of
- >WIndows instead of an integrated debugger.
-
- Because it's very hard to debug 16-bit applications from a 32-bit application.
- We found that we were spending far too much time trying to make this work, and
- not succeeding.
-
-